-
Notifications
You must be signed in to change notification settings - Fork 5.5k
Adding redirects for /components child pages #16381
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
WalkthroughThis update modifies the Next.js configuration file for documentation by adding four new permanent redirect rules. These rules redirect specific paths under Changes
Sequence Diagram(s)sequenceDiagram
participant User
participant Next.js Server
User->>Next.js Server: Request /components/guidelines/
Next.js Server-->>User: Redirect to /components/contributing/guidelines/
User->>Next.js Server: Request /components/actions-quickstart/
Next.js Server-->>User: Redirect to /components/contributing/actions-quickstart/
User->>Next.js Server: Request /components/sources-quickstart/
Next.js Server-->>User: Redirect to /components/contributing/sources-quickstart/
User->>Next.js Server: Request /components/typescript/
Next.js Server-->>User: Redirect to /components/contributing/typescript/
Possibly related PRs
Poem
Warning There were issues while running some tools. Please review the errors and either fix the tool's configuration or disable the tool if it's a critical failure. 🔧 ESLint
docs-v2/next.config.mjsOops! Something went wrong! :( ESLint: 8.57.1 Error [ERR_MODULE_NOT_FOUND]: Cannot find package 'jsonc-eslint-parser' imported from /eslint.config.mjs ✨ Finishing Touches
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. 🪧 TipsChatThere are 3 ways to chat with CodeRabbit:
Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments. CodeRabbit Commands (Invoked using PR comments)
Other keywords and placeholders
CodeRabbit Configuration File (
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Actionable comments posted: 0
🧹 Nitpick comments (1)
docs-v2/next.config.mjs (1)
339-358: New component redirects are correctly added.
The four entries for/components/guidelines/,/components/actions-quickstart/,/components/sources-quickstart/, and/components/typescript/mirror the existing redirect patterns (trailing slash,permanent: true) and point to the right targets under/components/contributing/.Tip: these rules only catch the root pages. If you expect nested sub‑paths (e.g.,
/components/guidelines/intro), consider adding dynamic catch‑all redirects or consolidating into a single regex‑based rule to reduce duplication:+ { + source: "/components/guidelines/:path*/", + destination: "/components/contributing/guidelines/:path*/", + permanent: true, + }, ...Or group all four in one rule:
{ source: "/components/:section(guidelines|actions-quickstart|sources-quickstart|typescript)/:path*/", destination: "/components/contributing/:section/:path*/", permanent: true, }
📜 Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro
⛔ Files ignored due to path filters (1)
pnpm-lock.yamlis excluded by!**/pnpm-lock.yaml
📒 Files selected for processing (1)
docs-v2/next.config.mjs(1 hunks)
⏰ Context from checks skipped due to timeout of 90000ms (2)
- GitHub Check: pnpm publish
- GitHub Check: Lint Code Base
* Adding redirects for /components child pages (#16381) * [Components] xendit #16278 Sources - New Invoice Actions - Create Invoice - Create Payout - Get Payment Status * pnpm update * some adjusts * some adjusts * pnpm update * some adjusts --------- Co-authored-by: Danny Roosevelt <[email protected]>
WHY
Summary by CodeRabbit